Libris Britannia 4

home *** CD-ROM | disk | FTP | other *** search

/ Libris Britannia 4 / science library(b).zip / science library(b) / COMMUNIC / BULLETIN / 0818B.ZIP / TPB-INST.MAN < prev next >

Wrap

Text File | 1987-12-01 | 49KB | 1,201 lines

System Installation Manual for TP-Board Version 2.0 Copyright (c) 1987 by Jon E. Schneider TP-Board and the associated support files are Copyright (c) 1987 by Jon Schneider. Non-commercial use and public distribution of this system is permitted. All commercial rights are reserved. TP-Board is based on the Pascal Integrated Communications System (PICS), Copyright 1986, 1987 by Les Archambault. This software is being distributed with his knowledge and consent. A large portion of the TP-Board code is an exact duplicate of the PICS code. CONTENTS I. Minimum System requirements II. Installation of a new system Step 1. Preliminaries Step 2. Editing the system files Step 3. Establishing the System organization Step 4. First run of the program to create new data files and setup the system defaults. Step 5. Set System and Purge parameters III. Installation of TP-Board if you are already running PICS IV. Enabling the remote 'Shell to DOS' V. Configuring TP-Board for Operation under SEAdog ================================================================== I. System requirements ================================================================== In order to run TP-Board, you must have an IBM compatible computer. It must be equipped with at least 256k, at least one serial port, and be capable of running MS-DOS 2.0 or later. If you want to run it under SEAdog and/or a multitasker, then you should have at least 384k free. You also must have a Hayes compatible modem, or at least one that is Hayes command set compatible. The following modem switch settings are assumed: 1 = up DTR supported, do not force to always logic true. 2 = down Send result codes as digits. 3 = down Send result codes to the host. 4 = up Echo characters when in command state (off line). 5 = down Do not answer the telephone. 6 = up DCD supported, do not force to always logic true. 7 = up Single line RJ11 telephone connection to modem. 8 = down Enables command recognition when in command state. A hard disk is not necessary, but is highly recommended. TP- Board will run on a 2 floppy system, but since it makes heavy use of overlays, it will run much slower on a floppy based system. There are several external programs that TP-Board requires for it's operation. They are DSZ, QMXFER, and PKXARC. If you wish to utilize the 'Shell to DOS' capabilities, then you will also need X00.SYS, WATCHCD (included in the X00 Archive), and GATEWAY2. If you want to utilize TP-Board's support for FidoNet, then you also must purchase a copy of SEAdog. I have tied all of the Fido-Net functions to SEAdog, and none of the other mailer programs will work (i.e., Dutchie or BinklyTerm). ================================================================== II. INSTALLATION OF A NEW SYSTEM ================================================================== STEP 1. PRELIMINARIES I would suggest that before you try installing TP-Board, you sit down and decide how you want the system organized. A little planning now will save a lot of time later. TP-Board, it's overlays and data files, and all external support programs must be located in one directory. If you are limited to one hard disk, then it's best to create a sub- directory called TP-Board directly below the root directory. If you have more than one hard drive, then you will probably want to use the root directory of the second drive. The files that need to reside in the system directory are; TP-BOARD.COM, .000, .001, .002, .003, and .004 QUOTES.TXT, SYSMSG.TXT, and SYSMSGG.TXT OTHERSYS.LST and BADNAMES.LST SETUP.COM RENUMBER.COM (Only if using FidoNet) DSZ.COM QMXFER.COM PKXARC.COM The following files are needed only if you shell to DOS REMOTE.BAT WATCHCD.COM TP-Board will create quite a few new files on it's first run. They will all have the extension BB#, and must stay in the system directory. Some of the external support programs also create their own files, but there is no harm done if they get lost or deleted. Once you've decided which directory you will be running TP-Board from, copy the files shown above to that directory. Try to avoid having any other files in that directory. It makes system backups and maintenance alot easier if only TP-Board files are located there. In order for the 'Shell to DOS' and external protocol functions to work properly, TP-Board must know how to find COMMAND.COM. Make sure that it is in the path that is active when TP-Board is running. STEP 2. EDIT THE SYSTEM MESSAGE FILES There are two system message files, SYSMSG.TXT and SYSMSGG.TXT. These files contain the various menus and messages that are used by TP-Board. Both files will need to be edited to reflect your particular systems information. There is also a text file of 'Quotes' that you can edit. All of the individual graphics screens used in SYSMSGG.TXT are in seperate files to facilitate their editing with an ANSI editor. I would recommend ANSIPAINT, as it is what I used to create them. Just edit each file individually, and when you have finished editing them, save them as individual files. Then using your normal text editor, block read them into the SYSMSGG.TXT file into their respective locations. Be SURE that when you save them from the ANSI editor that you set a maximum line length of 79 characters. Also be sure that the text editor that you use to edit the .TXT files does not alter a characters 8th bit. Whenever TP-Board first starts up, it tries to locate the files QUOTES.BB#, SYSMSG.BB# and SYSMSG.BB#. If it can't find them, it creates new ones from the QUOTES.TXT, SYSMSG.TXT and SYSMSGG.TXT files. The only way to get the changes you make in the .TXT files to be recognized by TP-Board is to delete the respective .BB# file and copy the new .TXT files over the previously existing one in the system directory. Editing ANSI graphics, and determining how to correctly get the edited screen into it's proper place is something that takes a little time to get the hang of. I will not assist in the process, so keep trying till you get it right. You WILL get the hang of it sooner or later. The other files that you will want to edit are OTHERSYS.LST (the listing of other local systems), and BADNAMES.LST (a list of names that are NOT allowed on the system). STEP 3. ESTABLISHING THE SYSTEM ORGANIZATION A program named SETUP.COM has been included in the TP-Board distribution package. It will create the System Organization file named SECTION.BB#. In this new file will be minimum required message areas and file sections as discussed above. Later, the same program can be used to edit and add entries as desired. Initially there are no conferences or Articles provided, nor are they needed to get the system running. I recommend that you use the minimum organization provided by the setup program until the system is up and running. To make TP-Board robust enough to withstand both incorrect entries and malicious attacks against the system, a simple but effective method is used: an access level, ranging from 0 to 255, is assigned to each user. The Message Areas and File Areas (which are accessed by name) are also assigned an access level. Users are able to gain access to any named File Section or Message Area if it's access level is less than or equal to his. The exception to this rule is Conferences. Users can gain access to a conference if their access level is higher than the level of the conference, but usually the conferences are set high enough so that only the Sysop and assistants can access it this way. There are seven flags contained in each user record. The Sysop may set these flags from the Sysop subsystem edit user command. If the flag for a particular conference is set, the user has access to that conference regardless of his access level, or the access level for the conference. When a user record is first created, none of the flags is set. The recommended levels of User access are defined as follows. (You should follow this guide when setting up access levels for the named Message Areas and File Sections described below.) 0-10 Twit - will be logged off immediately 11-20 Unvalidated user - limited message and files access 21-249 Normal user - full message and files access 250-254 Alternate sysops 255 Sysop The TP-Board system consists of four sub-systems: 1. The Messages Sub-System. 2. The Files Sub-System. 3. The Utilities Sub-System. 4. The Sysop Sub-System. The MESSAGE subsystem consists of named 'MESSAGE AREAS' where callers can read and leave messages. In addition there are 'ARTICLES' that can be read by callers. Each 'Message Area' and 'Article' is assigned a minimum user access level by the sysop. the Drive/User location for each 'Article' is also sysop definable. POST This is the MESSAGE AREA every user 'sees' initially. The access level of this area will be set to zero. SYSTEM This MESSAGE AREA is special since ALL messages (including those that have been erased) will be visible. IT IS IMPORTANT that the access level of this area be left high enough that normal users do not have access. To avoid potential problems, the access level for this area this area will be set at 250. The FidoNet and EchoMail areas are not accessible from this area. FIDO-NET This MESSAGE AREA is optional, but without it, all of the TP-Board functions relating to FidoNet mail will be inoperative. It can be setup on the initial run of SETUP, or it can be added at a later date. -??????? Any MESSAGE area that has a '-' as the first character will be handled as an EchoMail conference. Messages entered here will only be mailed after being processed by whatever EchoMail utility you use. They can also be set up as TP-Board conferences if you so desire. There are no required Articles or EchoMail conferences. You may enter any that you want after you have an operating TP-Board system. The FILES sub-system is a group of named 'FILE SECTIONS' where files available for distribution (download) and receipt (upload) are kept. Access to these Sections is controlled by the minimum user access level set by the sysop. The Drive location for each Section is sysop definable. SYSTEM This FILE SECTION is the location for all of the TP-Board system and data files. LOGIN This is the FILE SECTION every user 'sees' initially. The access level of this area will be set to zero. NEWIN This is the FILE SECTION into which uploads will be placed. The access level of this area will be set to 20, the default access level for validated users. There is no fixed limit to the number of MESSAGE AREAS, FILE SECTIONS and ARTICLES on the system, but remember that the names and descriptions of these will be stored in memory and might limit the operation of the system if you have too many. The Utilities and Sysop sub-sections require no special setup. STEP 4. RUN TP-BOARD TO CREATE NEW FILES AND LOGIN AS SYSOP The first time TP-Board is run, it will automatically create all the data files that it needs on the same drive as the TP- Board object files, and will announce that it is doing so. If successful the screen will clear and start randomly moving the cursor around. This is the normal idle state for TP-Board. At this time TP-Board is waiting for: 1) A signal from the modem indicating a remote user call. 2) a command from the console indicating a local user. (^L) 3) a command from the console to show system status. (CR) Enter a CONTROL L at the sysop console (telling TP-Board that you want to use the system locally). After the "FIRST name:" prompt appears, enter the name "SYSOP." Do NOT use your first and last name. Not finding SYSOP, the system will prompt for a password - enter one of your choice. You are now logged into the system as the Sysop with an access level of 255 (the max). If you want to be on the system with your name, re-sign in after login as Sysop. This will allow you to send and receive messages as either Sysop or using your real name. C A U T I O N !!! ----------------- It is VERY IMPORTANT that you log in as sysop before putting the system up for others to use. There are folks out there who will try to log in as sysop. If you have not set your password, they will set it for you and will consequently have full sysop level access. Files that TP-Board has created and will use in the future: MESSAGE.BB# The text of messages in the message file. SUMMARY.BB# Message headers and pointers to the text in the MESSAGE.BB# file. USERDAT.BB# The user file random record data file. USERIDX.BB# The Turbo Access index to USERDAT.BB#. SECTION.BB# The system organization random record file. LOG.BB# Coded log of system use. STATS.BB# Coded record of system usage by time & date. NEWIN.BB# Records of Uploads & info about them. SYSMSG.BB# Random record file made from SYSMSG.TXT file. SYSMSGG.BB# Random record file made from SYSMSGG.TXT file. QUOTES.BB# Random record file made from QUOTES.TXT file. ECHO.BB# The EchoMail conference file containing the user record offset to each conference. CONFIG.BB# Sysops system specific configuration info. Other than the SYSMSG.TXT file, these files are not meant to be edited by the sysop with a text editor. TP-Board has routines built in that will handle these files. In addition, TP-Board can create text files from the Messages and Log files when the Audit feature is used by the Sysop. This will be discussed in detail in the Theory of Operation Section of this manual. In this way, you have the ability to generate a text file from the random files shown above. Be sure to test the system from a remote computer using a modem, as this is the only way to be sure that the modem dependent routines are working properly. STEP 5. SET SYSTEM AND PURGE PARAMETERS SYSTEM PARAMETERS Once you are sure that the system is working properly, it is necessary to set up all of your system specific defaults. You will do that by using the <C>hange parameters command from the SysOp's menu. You will want to change the System parameters, and the Purge parameters. The Fido parameters need only be set if you intend to use the FidoNet capabilities of TP-Board. TP-Board has built in routines for guarding against your disks becoming full and causing a crash. As the disks become full, a controlled shutdown of functions takes place. The next five settings control when this takes place. When any of the limits are reached, TP-Board will display a message to the Sysop on the local console during the 'bouncing cursor' routine while it is waiting for the next caller. This occurs about every fifth 'bounce' of the cursor. * Min disk space req to allow uploads -------------------------------------- Files that are uploaded to TP-Board are written to the NEWIN section in the files sub-system. When there is less than this value (in K bytes) of free space left on the disk, callers are not permitted to send files to TP-Board. This test operates on the drive set (with the Setup program) for the NEWIN section. In the case of conferences the uploads will go directly to the drive that you have set with the Setup program. Unless this is the same drive as the NEWIN section, no checking for a full disk will be done. Distribution value = 50 (K) * Min disk space req to allow new users ---------------------------------------- This value represents the minimum disk space on the system disk (where the .COM file and overlays reside) to continue to allow new callers to register on the system. If less than this amount of space is left, the caller will be told that new logins can't be accepted and asked to call in later. Distribution value = 25 (K) * Min disk space req to NOT limit msg. length ---------------------------------------------- When there is less than this amount of free space available on the system drive, TP-Board will limit the number of lines that can be entered in a message to the value in the next setting. There is a separate setting (discussed later) for manually limiting the number of message lines all the time. Distribution value = 20 (K) * Msg. lines allowed when limited by disk space ------------------------------------------------ This is the number of lines that messages are limited to when there is not at least the amount of free disk space set in the value above. Distribution value = 10 (lines) * Absolute min disk space for any operations --------------------------------------------- If there is less than this amount of free space on the system disk all message entry is prohibited. Callers trying to enter messages are informed that there isn't enough disk space for messages. This value should be less than any of the values above. If there is less than the this amount amount of free disk space on the system drive, only callers already known to the system will be allowed in, and they will be able to do everything but upload and enter messages. Distribution setting = 5 (k) * Extra time added during certain hours ---------------------------------------- This toggle when ON and a call is received within the hours set, adds extra time (in minutes) to the caller's time allowed on the system (per day). This is done at the beginning of the session. When OFF, nothing happens. Distribution value = True (ON) * Hours extra time on system is added -------------------------------------- Between these hours, if the function is enabled, the users time limit will be increased by the number of minutes set below. Distribution value = 2-6 * Minutes of extra time to be added ------------------------------------ This is how much time (in minutes) will be added to the users daily time limit during the above times. Distribution value = 20 * Allow caller Chat -------------------- A toggle that when OFF prevents all attempts for callers to chat with the Sysop. The caller is told that the Chat function is not active. When the toggle is ON, the Chat function responds to the limits set in the following values. Distribution value = True (ON) * Hours Chat allowed --------------------- The hours during which the Sysop will be paged on the local system console. Outside of these hours the caller will be told what the Chatting hours are, but no paging of the Sysop will be done. These settings are in whole hours only, no minutes. All values for hours use a 24 hour notation (0-24). Distribution value = 0-24 * Seconds to wait before input timeout --------------------------------------- This value sets the time (number of seconds) that the system will wait for input from the modem (usually at prompts). After this number of seconds with no input (typed by the caller) TP- Board will print the message ++ Input Timed Out ++, log off the caller and wait for the next call. This doesn't affect the local console that the Sysop uses. Distribution value = 300 (seconds) * Max Tries for names, password before hangup ---------------------------------------------- The number of times TP-Board will allow a user to attempt password or name entry. If this number is exceeded, the system will disconnect with a message. Distribution value = 4 * Automatic Macro operation --------------------------- This toggle when ON enables the execution of the Macro string at the time set. When OFF, no macro execution takes place. Distribution value = True (ON) * Starting hour for auto macro execution ----------------------------------------- The hour (0-24) to start executing the macro string. Since this feature finishes when the last command is processed, there is no STOP setting. Distribution value = 4 (4 A.M.) TP-Board has the ability to execute commands automatically and unattended, just as if the sysop were sitting at the local console. This feature is called Macro Processing. (A macro is a string of characters and delimiters which represent commands.) If the Auto Macro processing is ON and the current hour is greater than the hour set for auto operation, TP-Board will wait for the current caller to hang up (if there is a caller) then it will make the modem busy to prevent more calls. Then it will log the sysop into the system automatically and pass the current Macro string to the multiple command buffer for execution. After completion of the commands, TP-Board will log off the system (this must be the final command in the Macro string) and put the phone back on the hook. The maximum length of the Macro string is 80 characters, including delimiters (spaces, commas, semi-colons). Care must be taken to make sure all required key strokes are included in the Macro string, especially the final command to log the Sysop off the system. Carriage returns can be put into the string by using an up arrow and M (^M). It is the Sysop's responsibility to make sure of this, or the system will sit and wait for further input from the local keyboard! I recommend that before making the Macro automatic it be tested by the Sysop. * Limiting number of max message lines --------------------------------------- This toggle when ON limits the length of all messages entered to the number of lines in the next definition. It is useful when lots of messages are being entered on a system with limited disk space. This setting has nothing to do with the limiting of message lines that happens automatically when the disk fills up to the settings above. Distribution value = False (OFF) * Maximum number of message lines allowed ------------------------------------------ The number of lines that messages will be limited to when the above toggle is ON. During message entry, callers will be warned 2 lines before the end of the message is reached. Distribution value = 100 * Restrict 300 baud callers from using system ---------------------------------------------- This toggle when ON will not accept callers at 300 baud between the preset hours. After connecting with the system they will be notified of the hours when 300 baud calling is restricted, then TP-Board will hang up. When OFF no restrictions will be applied to 300 baud callers. Distribution value = False (ON) * Hours to restrict 300 baud use --------------------------------- The hours (0-24) during which restriction of 300 baud callers occurs. Distribution value = 17-24 * Default Up/Dn ratio allowed ------------------------------ The value entered here is the ratio that is set for all users on their FIRST login. You can set their ratio after that to anything you want, and this value will not affect that setting. Distribution value = 20 * Restrict public messages until sysop approves ------------------------------------------------ This toggle when ON will automatically flag all messages entered as Public by the sender. They will not be available for viewing until released by the Sysop. Only messages entered after the toggle has been turned on are affected. When OFF, messages marked Public will be immediately available for viewing. Distribution value = False (OFF) * Caller number ---------------- This is the number of calls made to your system since the LOG.BB# file was created. You may want to change this number if you were previously running a system, and want the total to reflect the total number of calls received on both systems. Distribution value = 0 PURGE PARAMETERS * Time allowed on system ------------------------- The values set here are the defaults that TP-Board uses for 'Time Allowed on System'. Whenever a new user logs on, he is only allowed to be online for the amount of time that you set as the time limit for un-validated users. Distribution values validated = 50 un-validated = 20 * Access Level --------------- The values set here are the defaults that TP-Board uses for the user's access levels. Whenever a new user logs on, he is automatically set to the access level defined here for un- validated users. Distribution values validated = 50 un-validated = 20 NOTE: If you set access level of un_validated users the same or greater value than the setting for validated users you are creating an OPEN system where callers DO NOT require verification by the Sysop before obtaining the same status as validated users. * Days to retain inactive user ------------------------------- The number of days allowed to elapse between calls before the inactive user is purged from the system. For example, 180 and 61 will allow unvalidated users to remain on the system for 61 days between calls and validated users 180 days between calls before being deleted from the user file during a purge operation. Distribution values validated = 180 un-validated = 61 * Days to retain unread and read messages ------------------------------------------ The number of days allowed to elapse before unread and read messages, respectively, are automatically deleted from the message file during a purge operation. Public messages are never marked as read and thus will be available until explicitly deleted or until they "expire" as determined by 'un-read days.' All messages are subject to these time limits unless they have been marked as <P>rotected by the Sysop. Any messages marked as deleted remain in the message file until the next purge operation, but are automatically purged even though the number of days is less than the values above. Distribution values read = 30 un-read = 60 ================================================================== III. INSTALLATION OF TP-BOARD FOR THOSE ALREADY RUNNING PICS ================================================================== !!!!!!!! IMPORTANT !!!!!!!!!! Before attempting to install TP-Board on an already established PICS system, make a complete back-up of ALL of the PICS files. Make sure that you move them off of the computer, and store them in a safe place. It is a fairly simple matter to convert from PICS to TP- Board without the loss of any data. There are several incompatibilities between TP-Board's files and PICS files, but they can be handled with no problems. The biggest difference is in the users record. PICS uses a record length of 123 bytes, while TP-Board uses a length of 256 bytes. There is a program in the distribution Archive called CONVERT that will convert your old users records to the new format. After having backed up all of your old records, copy all of the TP-BOARD files from the distribution Archive to your system directory. Then edit the SYSMSG.TXT and SYSMSGG.TXT files as detailed earlier in this document. There are new menu options available, and they are not shown in your old files. Now delete CONFIG.BB#, SYSMSG.BB#, and USERIDX.BB#. Then run the program CONVERT. After it completes, delete USERDAT.BB#, and rename the files as instructed by SETUP. This completes the process of converting your old records. Before running TP-Board, copy the program SETUP to an empty directory. Run it, and answer the questions as if setting up a new system. After it completes, erase the SECTION.BB# file that it created, and copy the ECHO.BB# file to your system directory. You will have lost all of your old default configuration settings, so it will be necessary to run TP-Board, and set the new ones from the SysOp's menu. You will discover a few new parameters have been added, but they are all self-explanatory. There are many differences between PICS and TP-Board, but you will discover them rather quickly if you have been running PICS for any length of time. The biggest changes, and the ones that require the most explanation, are all related to FidoNet, and are covered in the SEAdog section of this manual. ================================================================== ENABLING THE REMOTE SHELL TO DOS ================================================================== This feature is one that I would not recommend enabling, but for those users that insist on having the capability, I have allowed them the option of implementing it. As long as TP-Board or SEAdog is in control of the system, I can pretty much guarantee the systems security. Once you let DOS or some other program have control, you are risking lock-ups and other forms of disaster. If the file REMOTE.BAT does not exist in the system directory, then the 'Shell to DOS' is only available while logged onto the local console. If TP-Board is being run remotely, and the 'X' command is given from the SysOp's menu, nothing will happen. I've included a sample REMOTE.BAT file on this page. In order for it to work properly, you must have installed two device drivers at boot time via CONFIG.SYS. They would be invoked with the following command lines; DEVICE=GATEWAY2.SYS -d -1 ; assumes COM1 DEVICE=X00.SYS e 0 The GATEWAY device driver is what DOS will be re-directed to, and X00.SYS is where the carrier watchdog (WATCHCD) memory resident code resides. If carrier is lost while in DOS, a complete system re-boot will occur. SAMPLE REMOTE.BAT FILE @echo off watchcd com1 on ; activate carrier watchdog ctty gate1 ; re-direct I/O command ; invoke DOS shell ctty con ; I/O back to normal watchcd com1 off ; de-activate carrier watchdog Remember, you are risking major problems if you implement this feature. I STRONGLY suggest that you don't use it. If you insist on utilizing it, you do so at your own risk. ================================================================== CONFIGURING TP-BOARD FOR OPERATION UNDER SEADOG ================================================================== FidoNet is a public network of electronic mail hobbyists who send and receive mail using the FidoNet protocol. It originally began as a network of FIDO bulletin boards, but there are now many different systems participating in the net. TP-Board is designed to handle messages that are in the FidoNet standard format. It's own message base is NOT FidoNet compatible, so it must be told if a message area is for use in FidoNet. The system installation manual covers the necessary procedures for setting up FidoNet compatible message areas. TP-Board does NOT handle the creation of mail packets, routing, or sending of mail to other systems. That is all handled by a program called SEAdog, which is run as a front end to TP- Board. SEAdog is a commercial product from System Enhancement Associates, 21 New Street, Wayne, NJ 07470. It can be operated as a stand alone electronic mail package, or can be used as the front end to a bulletin board system. It costs $99, and is well worth the price. If you want to participate in FidoNet, you must already own a copy of SEAdog, and have already installed it on your system according to the instructions supplied with it. It is up to you to obtain a network address from your network or regional FidoNet coordinator. I am going to make the following assumptions about your SEAdog installation. You have all of the SEAdog command files in a directory called 'C:\MAIL', and you have three directories under it, 'MESSAGES', 'FILES', and 'HELP'. I am also going to assume that you have TP-Board installed in a directory called 'C:\TP-BOARD', that COMMAND.COM resides in the root directory on C: drive, and that your DOS path includes both the root directory of drive C: and the SEAdog mail directory. If your installation does not fit these criteria, then you will need to change the batch files that I use in these examples, and your DOS path. The changes will be very minor. The first thing you will need to do is run SETUP and create a message area called 'FIDO-NET'. The name MUST be exactly as shown. You may also create any EchoMail conferences that you desire at this time, or you can add them later. If you do add an EchoMail conference, it's first character MUST be a '-', i.e., '-TANDY'. After adding the FIDO-NET and EchoMail message areas, a separate subdirectory must be created for each EchoMail area. These subdirectories must be directly under the directory that was choosen as the location for the FIDO-NET area (usually the SEAdog MAIL area). For example, if your SEAdog mail directory's path was 'C:\MAIL\MESSAGES', then you would set up the FIDO-NET area's path as 'C\:MAIL\MESSAGES' also. Then the path to an EchoMail conference called '-TANDY' would be 'C:\MAIL\MESSAGES\-TANDY'. Once you have set up the necessary directories, run TP- Board, go to the SysOp's menu, and using the <C>hange parameters command, select the <F>ido Net sub menu. Then set the paths listed to reflect your current set-up. The path to the Fido-Net message area would in this case would be 'C:\MAIL\MESSAGES'. The second path (SEAdog's Network lists) is the path to the two files that SEAdog creates from the nodelist. They are NETLIST.DOG and NODELIST.DOG. TP-Board must know where these files are located on your system. They are usually kept in the main SEAdog mail directory ('C:\MAIL' in this case). The maximum number of EchoMail conferences that you can have is 62, and the maximum number of messages in any one of these areas is 1024. DO NOT use any of the FidoNet message renumbering utilities. There are counters for high message read for each message area in the users record, and the renumbering of messages with another renumbering utility will throw the counters off. There is a RENUMBER program included with TP-Board, and it will properly handle all the needed functions. To avoid problems, erase any other renumbering programs from your disk. The program MUST be run from the TP-Board system directory. In order to have TP-Board operate properly under SEAdog, everything must be run from a batch file. This allows SEAdog to call TP-Board once it determines that it has a human caller, and it allows control to return to SEAdog once the caller logs off. The batch files also allow SEAdog to pass control to other external programs at pre-determined times. The files can get quite complex, especially if EchoMail is going to be processed. The first example used here is fairly simple. Create a batch file called BBS.BAT, and place it in a directory that is included in your DOS Path. I have mine placed in the root directory of the C: drive. Once you have created the batch file, you will always invoke TP-Board using the command BBS. Here is an example BBS.BAT file. SAMPLE BBS.BAT FILE @echo off :loop ; Keep coming here c: cd \mail ; Change to SEAdog's dir cls mailer ; Invoke SEAdog if errorlevel 100 goto tpblocal ; F10 will log you on locally if errorlevel 10 goto exit ; Any other will exit if errorlevel 5 goto tpbmacro ; External SEAdog event goto exit :tpbmacro ; Called as an external event c: cd \tp-board ; Change to TP-Board's dir tpb 98 ; Invoke TP-Board, execute macro, and log-off goto loop ; Rerun SEAdog :tpblocal ; To log on to TP-Board locally c: cd \tp-board ; Change to TP-Board's dir tpb 99 ; Tell it you want to logon locally goto loop ; Return to SEAdog :exit ; Quit, and return to DOS In the example shown on the previous page, TP-Board was called with parameters. What the parameters are will determine what TP-Board does upon being invoked. If it is invoked with two parameters, and the first parameter is a valid baud rate, then it assumes that carrier has already been established, and that the first parameter was the baud rate, and the second parameter is the time in minutes until the next SEAdog event. TP-Board will examine the 'Time Till Next Event' parameter, and if it is less than the callers alloted time, it will adjust their time downwards, and let them know that an adjustment to their time allotment was made. If the first parameter is a 99, then TP-Board will assume that you want to log on locally, and will exit to DOS when you log off. If the first parameter is a 98, then TP-Board will logon as SYSOP, execute the pre-configured macro, and then exit back to DOS. This is the ONLY way to get the macro to execute automatically if you are running TP-Board under SEAdog. You should also create a batch file called RUNTPB.BAT. This file will be placed in SEAdog's 'MAIL' directory, and is what SEAdog will call to invoke TP-Board. Here is a sample RUNTPB.BAT file. SAMPLE RUNTPB.BAT FILE @echo off cls c: cd \tp-board ; Make sure we're in the right dir tpb %1 %2 ; Invoke TP-Board with baud rate and time to event cls cd \mail ; Switch back to SEAdog's dir It is also necessary to configure SEAdog by using the CONFIG.DOG file. I have included a sample CONFIG.DOG file on this page. It can be much more complex than the example, but I'm trying to keep it as simple as possible for first time users. SAMPLE CONFIG.DOG FILE Name Jon Schneider Node 381/23 Mail C:\MAIL\MESSAGES Files C:\MAIL\FILES Help C:\MAIL\HELP Modem Courier Modem Reset AT H1 S0=0 Dial 1-915- Log SEADOG.LOG Brief BBS RUNTPB *b *t *d ;invoke a BBS Event A All 2:00 3:00 ;national mail hour Event S All 8:00 17:00 Crash Dynamic ;crash mail Event X5 Mon 5:00 ;this is when I execute the macro The setup shown here is a minimal FidoNet setup. It doesn't include any EchoMail conferences or automated processing. I would recommend it as the setup to be run when fist attempting to run your system in the Net. Once you are sure that everything is running properly, you will more than likely want to expand the setup. TP-Board also supports cost accounting. When the Nodelist is compiled using XLATLIST, and the XLATLIST.CTL file is set up properly, each node entry in the nodelist will have a cost per message field. This figure is used by TP-Board everytime a user enters or replies to a message. The user is allowed to enter messages to any node that is set up as being free, but unless the user has a positive account balance greater than the cost of the message, he cannot enter a message to a node that requires a toll call. The SysOp can change the users account balance from the <E>dit users menu, and the user will be shown his current balance whenever he logs in. This allows the SysOp to allow selected users to send mail to any node, and still allows all other users access to any of the local nodes.